Skip to content

Fix path for Chrome DevTools external plugin#1784

Open
aaronpowell wants to merge 2 commits into
stagedfrom
fixing-chrome-devtools-plugin
Open

Fix path for Chrome DevTools external plugin#1784
aaronpowell wants to merge 2 commits into
stagedfrom
fixing-chrome-devtools-plugin

Conversation

@aaronpowell
Copy link
Copy Markdown
Contributor

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the staged branch for this pull request.

Description

Correct the path for the Chrome DevTools external plugin to point to the correct folder structure in the repository.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

Additional Notes

No additional information or context for reviewers.


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Copilot AI review requested due to automatic review settings May 20, 2026 23:10
@github-actions github-actions Bot added external-plugin PR updates plugins/external.json plugin PR touches plugins website-update PR touches website content or code labels May 20, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aligns external plugin metadata and website linking behavior with the repository’s external plugin policy by ensuring source.path represents a plugin root folder (or / for repo root), not a plugin.json file path.

Changes:

  • Fix external plugin URL generation to treat source.path: "/" as “repo root” (link to the repo, not tree/main//).
  • Update the Chrome DevTools external plugin entry to stop pointing source.path at a manifest file.
  • Strengthen and document validation guidance so source.path cannot target plugin.json directly, and clarify the issue template/help text.
Show a summary per file
File Description
website/src/scripts/pages/plugins-render.ts Avoids generating a GitHub tree URL when source.path is / (uses repo root instead).
website/src/scripts/modal.ts Same / handling fix for external plugin links in the modal.
plugins/external.json Removes Chrome DevTools source.path that incorrectly pointed at a manifest file; minor keywords formatting normalization.
eng/external-plugin-validation.mjs Allows source.path: "/" and rejects paths that point directly to plugin.json; improves error messaging.
CONTRIBUTING.md Clarifies source.path expectations: / for root or a repo-relative plugin root folder (not plugin.json).
.github/plugin/marketplace.json Updates generated marketplace entry to match corrected external plugin metadata.
.github/ISSUE_TEMPLATE/external-plugin.yml Clarifies what to enter for plugin path and updates the placeholder to a folder path.

Copilot's findings

  • Files reviewed: 7/7 changed files
  • Comments generated: 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external-plugin PR updates plugins/external.json plugin PR touches plugins website-update PR touches website content or code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants